Designing for Auditability: Keeping the Master Design Record Accurate as Devices Evolve

With FDA’s Quality Management System Regulation now aligned more closely with ISO 13485, medical device companies are under greater pressure to maintain documentation and traceability throughout development. At the center of that effort is the Master Design Record, a living record that should evolve with the device itself rather than be reconstructed at the end of development.

That shift has important implications for engineers.

Engineers may not always see themselves as part of the quality process. Their focus is often on solving technical problems, testing concepts, refining designs, and moving the product forward. Capturing engineering decisions, rationale, and traceability can feel like something Quality or Regulatory will organize later. That mindset needs to change.

Every engineering decision contributes to the device’s quality history. When an engineer changes a component, material, requirement, design output, or test approach, the Master Design Record should evolve with that decision. If the rationale, impact, supporting evidence, review, and approval are not captured when the change occurs, the organization may eventually have to reconstruct the story months later.

And, as I often tell teams, people forget. An engineer may look back at three CAD revisions and ask, “Why did I make that change?” The contract engineer who made the decision may no longer be with the company. Notes may exist, but no one knows where they were stored. The team is left trying to justify a past decision without a complete record of what happened or what else was affected.

The question is not whether every early idea requires a formal Engineering Change Order. During concept development, lab notebooks, sketches, test notes, and observations may be entirely appropriate. The problem arises when companies blur the line between concept exploration and formal product development.

Many startups build prototypes, conduct pilot work, and make meaningful design decisions before clearly defining user needs, product requirements, risks, and traceability. Then they try to recreate that engineering history afterward. That is where “we’re not ready yet” becomes dangerous.

From product launches to M&A and manufacturing trends, the MPO Source delivers the medtech news you need twice a week. Subscribe here!

I hear that phrase in several situations. An early-stage team may believe quality should wait until the design is more mature. A company raising capital may see a connected system as an expense to defer. Another organization may be preparing for clinical work but assume its spreadsheets, paper records, and existing tools are sufficient.

In each case, the company may be further along than it realizes. Once meaningful design decisions are being made, components are changing, prototypes are being evaluated, or clinical work is approaching, the organization is already creating the history it will later need to explain.

In my experience, a development team preparing for early clinical evaluation discovered a configuration discrepancy after several prototype and component revisions. Resolving the issue required additional manufacturing work and documentation updates, contributing to schedule disruption. The experience demonstrated how difficult it can be to maintain reliable design traceability when product information is distributed across multiple records and processes. The consequences extended well beyond documentation. The delay affected materials, testing, runway, and fundraising. Investors wanted to know why first-in-human work had not begun as planned. The company had to explain that a mistake required the product to be rebuilt.

That experience illustrates why auditability must be designed into the workflow early.

However, what does a real-time auditability workflow actually look like? It keeps the Master Design Record synchronized with engineering activity. When an engineer creates or modifies a requirement, identifies a new risk, updates a CAD model, changes a material specification, or completes verification testing, those activities should not exist in isolation. They should remain connected to related requirements, risks, design outputs, manufacturing records, reviews, and approvals. Instead of recreating those relationships months later, the workflow preserves the engineering intent behind each decision as the product evolves, allowing the design record to accurately reflect the current state of the device every step of the way.

For engineers, the goal should not be to add more administrative work. It should be to make traceability and design rationale a natural output of development.

A connected workflow does not make engineering decisions. It makes engineering decisions more informed. By showing upstream and downstream relationships in real time, engineers can evaluate the potential impact of a change before it is implemented, rather than discovering weeks or months later that another requirement, test, component, or manufacturing process was affected. That visibility allows engineers to make better decisions while maintaining a complete and accurate design record.

Ideally, information entered in systems such as CAD should remain connected rather than being repeatedly exported, uploaded, or re-entered elsewhere. Engineers should spend their time designing better products, not chasing disconnected information across multiple systems.

This is also where engineers begin to see quality differently. Traceability is no longer paperwork completed for an auditor. It becomes a practical engineering tool for evaluating change, preserving engineering intent, identifying gaps, and preventing unintended consequences.

Designing for auditability is not about asking engineers to document more. It is about building a workflow where quality records become a natural byproduct of engineering work. In practice, that comes down to three principles:

1. Maintain traceability continuously: Build and preserve relationships while the work is happening.
2. Evaluate every change: Even a seemingly minor modification can affect testing, biocompatibility, manufacturing, or risk.
3. Keep the record current, connected, and supported by evidence: Teams should be able to see what changed, why it changed, what was affected, and who reviewed and approved it.

When engineers begin working this way early, audit readiness stops being a separate event. The Master Design Record evolves alongside the device itself, accurately reflecting every significant engineering decision as it happens. Instead of reconstructing documentation at the end of development, organizations are continuously building the evidence needed to demonstrate both the quality of the product and the discipline of the engineering process behind it.

More insights from Enlil: Redefining OEM-CDMO Collaboration with a Development Traceability Platform

Maureen Gamarra is a product manager and medical device quality process expert at Enlil. One of the company’s longest-serving employees, she brings deep knowledge of design controls, traceability, change management, and the connected quality processes that support regulated product development. Her work focuses on translating real-world medtech challenges into practical workflows that help teams preserve engineering intent, maintain accurate product records, and make audit readiness a natural outcome of everyday development.